Skip to content

Symbolically Parametrized Modules#664

Draft
kimmeljo wants to merge 2 commits into
intel:mainfrom
kimmeljo:parametrization
Draft

Symbolically Parametrized Modules#664
kimmeljo wants to merge 2 commits into
intel:mainfrom
kimmeljo:parametrization

Conversation

@kimmeljo

@kimmeljo kimmeljo commented Jun 5, 2026

Copy link
Copy Markdown
Contributor

Description & Motivation

A limitation in the partial adoption path for ROHD is the case where a ROHD module is meant to be instantiated in a larger non-ROHD (ex: SystemVerilog) context and the larger context expects the ROHD module to be parametrizable at its build/synth time (i.e., after ROHD has generated its output representation for that context).

One option is to put the larger context into a generator framework but that can be a non-starter in some cases.

Hence, the goal is to enable ROHD to generate output that can be parametrized by the output context's build/synth flow. In this PR, we focus only on SystemVerilog.

Related Issue(s)

N/A

Testing

Many new unit tests as well as updates to existing unit tests with new test cases as needed.

Backwards-compatibility

Is this a breaking change that will not be backwards-compatible? If yes, how so?

The intent is for this to be fully backwards compatible. I.e., this is a new, additive construct.

Documentation

Does the change require any updates to documentation? If so, where? Are they included?

Dedicated documentation provided for this feature.

… that ROHD modules can generate parametrized SV.
@kimmeljo kimmeljo requested a review from mkorbel1 June 5, 2026 20:36
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

1 participant